This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

payloadcms-vectorize@1.1.0

Minor Changes

• #71 98bc41b Thanks @techiejd! - Add vector read primitives and the ability to retrieve stored embedding vectors.

  • vectorizedPayload.findByIds({ knowledgePool, ids, populateEmbedding }) — batch-fetch embedding records by id, returning Record<string, EmbeddingRecord | undefined> (misses map to undefined). Implemented across the pg, cf, and mongodb adapters.
  • vectorizedPayload.searchByEmbedding({ knowledgePool, embedding, where, limit, populateEmbedding }) — run a vector search directly from a raw embedding vector, skipping the query-embedding step. This is the "more like this" primitive: feed it the embedding returned by findByIds({ populateEmbedding: true }) to find similar content. Result shape and where filtering match search(). Unlike search(), it does not run reranking even on a pool configured with rerank, since rerankers operate on the original query text. Local API only.
  • populateEmbedding?: boolean option (default false) on search() and searchByEmbedding() — when true, each result includes its stored embedding vector. VectorSearchResult and EmbeddingRecord now expose embedding?: number[].

  Fix:

  • mongodb adapter search() now returns all stored fields (including extension fields) on each result, matching the pg and cf adapters for cross-adapter parity.

@payloadcms-vectorize/cf@1.1.0

Minor Changes

• #71 98bc41b Thanks @techiejd! - Add vector read primitives and the ability to retrieve stored embedding vectors.

  • vectorizedPayload.findByIds({ knowledgePool, ids, populateEmbedding }) — batch-fetch embedding records by id, returning Record<string, EmbeddingRecord | undefined> (misses map to undefined). Implemented across the pg, cf, and mongodb adapters.
  • vectorizedPayload.searchByEmbedding({ knowledgePool, embedding, where, limit, populateEmbedding }) — run a vector search directly from a raw embedding vector, skipping the query-embedding step. This is the "more like this" primitive: feed it the embedding returned by findByIds({ populateEmbedding: true }) to find similar content. Result shape and where filtering match search(). Unlike search(), it does not run reranking even on a pool configured with rerank, since rerankers operate on the original query text. Local API only.
  • populateEmbedding?: boolean option (default false) on search() and searchByEmbedding() — when true, each result includes its stored embedding vector. VectorSearchResult and EmbeddingRecord now expose embedding?: number[].

  Fix:

  • mongodb adapter search() now returns all stored fields (including extension fields) on each result, matching the pg and cf adapters for cross-adapter parity.

@payloadcms-vectorize/mongodb@1.1.0

Minor Changes

• #71 98bc41b Thanks @techiejd! - Add vector read primitives and the ability to retrieve stored embedding vectors.

  • vectorizedPayload.findByIds({ knowledgePool, ids, populateEmbedding }) — batch-fetch embedding records by id, returning Record<string, EmbeddingRecord | undefined> (misses map to undefined). Implemented across the pg, cf, and mongodb adapters.
  • vectorizedPayload.searchByEmbedding({ knowledgePool, embedding, where, limit, populateEmbedding }) — run a vector search directly from a raw embedding vector, skipping the query-embedding step. This is the "more like this" primitive: feed it the embedding returned by findByIds({ populateEmbedding: true }) to find similar content. Result shape and where filtering match search(). Unlike search(), it does not run reranking even on a pool configured with rerank, since rerankers operate on the original query text. Local API only.
  • populateEmbedding?: boolean option (default false) on search() and searchByEmbedding() — when true, each result includes its stored embedding vector. VectorSearchResult and EmbeddingRecord now expose embedding?: number[].

  Fix:

  • mongodb adapter search() now returns all stored fields (including extension fields) on each result, matching the pg and cf adapters for cross-adapter parity.

@payloadcms-vectorize/pg@1.1.0

Minor Changes

• #71 98bc41b Thanks @techiejd! - Add vector read primitives and the ability to retrieve stored embedding vectors.

  • vectorizedPayload.findByIds({ knowledgePool, ids, populateEmbedding }) — batch-fetch embedding records by id, returning Record<string, EmbeddingRecord | undefined> (misses map to undefined). Implemented across the pg, cf, and mongodb adapters.
  • vectorizedPayload.searchByEmbedding({ knowledgePool, embedding, where, limit, populateEmbedding }) — run a vector search directly from a raw embedding vector, skipping the query-embedding step. This is the "more like this" primitive: feed it the embedding returned by findByIds({ populateEmbedding: true }) to find similar content. Result shape and where filtering match search(). Unlike search(), it does not run reranking even on a pool configured with rerank, since rerankers operate on the original query text. Local API only.
  • populateEmbedding?: boolean option (default false) on search() and searchByEmbedding() — when true, each result includes its stored embedding vector. VectorSearchResult and EmbeddingRecord now expose embedding?: number[].

  Fix:

  • mongodb adapter search() now returns all stored fields (including extension fields) on each result, matching the pg and cf adapters for cross-adapter parity.